Repository navigation
Stage Workers.dev backend origin and enforce canonical authentication - #8
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stage the hosted backend at https://codexbot.appsolves.workers.dev so machine clients can reach it without changing the appsolves.dev zone's Bot Fight Mode. Enable workers_dev, keep preview_urls false and preserve the existing custom domain, Worker identity, D1, secrets, compatibility configuration, cron triggers and disabled merge gate.
The CLI and generated callers default to the new URL; explicit self-hosted origins remain supported. Update the actual onboarding page commands/canonical link, README, manifest and installation values. Privileged routes including webhooks now reject noncanonical request origins with HTTP 421 and no redirect. Retained aliases serve only public landing/health; OIDC audiences, HMAC, actor/install binding and the credential guard remain strict. Keep the reusable/Worker trust pin exactly 4ed6688.
OAuth AAD and profile paths remain origin-specific: old ciphertext cannot be reused. docs/origin-migration.md gives the staged enable/health/flip sequence, manual GitHub App webhook/setup changes, provider revocation fallback if the old endpoint is challenged, fresh new-origin sign-in, caller coordination and secure rollback. No ciphertext rebinding, profile copying or dual-audience window is introduced. The source-only manifest cannot change registered App settings.
Validation passed on Node 24: npm run check (130 tests, typecheck, lint, build), npm run test:clean, actual workerd/D1, actionlint for repository and proposed consumer caller, final and stage-1 Wrangler dry-runs, secret scan (zero findings) and diff check. Tests cover CLI defaults/overrides/profile names, exact audience, HMAC, Origin/host rejection, old-ciphertext rejection and public onboarding. A read-only account check confirmed the existing appsolves subdomain with Workers.dev currently disabled. Node health returned 404 without a challenge while disabled; deployed transport/webhook/OIDC/provider success is not claimed.
Do not merge, deploy, change App settings/credentials or remove the custom route without explicit authorization. Coordinate the separate caller PR through normal protection. Keep reviews paused during cutover; real ping delivery, fresh credential-only diagnostic and OAuth connection remain operator release gates before a separately authorized advisory/no-merge review. No production settings, zone security, secrets or inference were changed by this PR.